[INSTRUCTION: For sponsored TLDs, this part of the application is to be completed by the sponsoring organization. For unsponsored TLDs, the registry operator should complete this part of the application. Please refer to the Detailed Application Instructions for more information on the requirements for new TLD applications.
The operation of a TLD involves the implementation of policies on a very large number of topics. Applicants are urged to use their response to this part of the application to demonstrate their detailed knowledge of what topics are involved and their careful analysis and clear articulation of the policies they propose on these topics.
Please place the legend "CONFIDENTIAL" on any part of your description that you have listed in item F3.1 of your Statement of Requested Confidential Treatment of Materials Submitted.
Section III of this application applies only to applicants for restricted TLDs. Ordinarily, restricted TLDs should be sponsored.]
I. GENERAL TLD POLICIES (Required for all TLDs. Note that two special policy areas--policies during the start-up period and restrictions on who may register within the TLD and for what purpose--are covered in sections II and III below.)
E1. In General. Please provide a full and detailed description of all policies to be followed in the TLD (other than those covered in response to items E11-E21). If the TLD's policy on a particular topic is proposed to be identical to that reflected by a particular version of any of the following documents, it is sufficient for your response to identify the topic, to give a brief summary of the policy, and for the details to reference the document and section:
· ICANN Registrar Accreditation Agreement
· NSI Registrar License and Agreement
· ICANN-NSI Registry Agreement
· Uniform Dispute Resolution Policy
Your response should comprehensively describe policies on all topics to be followed in connection with the proposed TLD. The following items (E2-E10) are examples only and should not limit your description.
E2. TLD String. Please identify the TLD string(s) you are proposing. For format requirements for TLD strings, see the answer to FAQ #5.
E3. Naming conventions. Describe the naming conventions and structure within the TLD. E.g., will registrants have names registered at the second level (directly under the TLD, as in registered-name.com), or will the TLD be organized with sub-domains so that registered domain names are created at a lower level (as in registered-name.travel.com)?
E4. Registrars. Describe in detail the
policies for selection of, and competition among, registrars. Will domain-name
holders deal through registrars, directly with the registry operator, or some
combination of the two? What are the respective roles, functions, and
responsibilities for the registry operator and registrars? If registrars are to
be employed, how and by whom will they be selected or accredited? If the number
of registrars will be restricted, what number of registrars will be selected?
Have the qualifying registrars already been selected? On what basis will
selections among those seeking to be registrars be made, and who will make
them? If registrars are to be used, what mechanisms will be used to ensure that
TLD policies are implemented?
E5. Intellectual Property Provisions. Describe the policies for
protection of intellectual property. Your response should address at least the
following questions, as appropriate to the TLD:
E5.1. What measures will be taken to discourage registration of domain names that infringe intellectual property rights?
E5.2. If you are proposing pre-screening for potentially infringing registrations, how will the pre-screening be performed?
E5.3. What registration practices will be employed to minimize abusive registrations?
E5.4. What measures do you propose to comply with applicable trademark and anti-cybersquatting legislation?
E5.5. Are you proposing any special protections (other than during the start-up period) for famous trademarks?
E5.6. How will complete, up-to-date, reliable, and conveniently provided Whois data be maintained, updated, and accessed concerning registrations in the TLD?
E6. Dispute Resolution. Describe the policies for domain name and other dispute resolution. If you are proposing variations to the policies followed in .com, .net, and .org, consider the following questions:
E6.1. To what extent are you proposing to implement the Uniform Dispute Resolution Policy?
E6.2. Please describe any additional, alternative, or supplemental dispute resolution procedures you are proposing.
E7. Data Privacy, Escrow, and Whois. Describe the proposed policies on data privacy, escrow and Whois service.
E8. Billing and Collection. Describe variations in or additions to the policies for billing and collection.
E9. Services and Pricing. What registration services do you propose to establish charges for and, for each such service, how much do you propose to charge?
E10. Other. Please describe any policies concerning topics not covered by the above questions.
II. REGISTRATION POLICIES DURING THE START-UP PERIOD (Required for all TLDs)
E11. In this section, you should thoroughly describe all policies (including implementation details) that you propose to follow during the start-up phase of registrations in the TLD, to the extent they differ from the General TLD Policies covered in items E1-E9. The following questions highlight some of the areas that should be considered for start-up policies:
E12. How do you propose to address the potential rush for registration at the initial opening of the TLD? How many requested registrations do you project will be received by the registry operator within the first day, week, month, and quarter? What period do you believe should be considered the TLD's "start-up period," during which special procedures should apply?
E13. Do you propose to place limits on the number of registrations per registrant? Per registrar? If so, how will these limits be implemented?
E14. Will pricing mechanisms be used to dampen a rush for registration at the initial opening of the TLD? If so, please describe these mechanisms in detail.
E15. Will you offer any "sunrise period" in which certain potential registrants are offered the opportunity to register before registration is open to the general public? If so, to whom will this opportunity be offered (those with famous marks, registered trademarks, second-level domains in other TLDs, pre-registrations of some sort, etc.)? How will you implement this?
III. REGISTRATION RESTRICTIONS (Required for restricted TLDs only)
E16. As noted in the New TLD Application Process Overview, a restricted TLD is one with enforced restrictions on (1) who may apply for a registration within the domain, (2) what uses may be made of those registrations, or (3) both. In this section, please describe in detail the restrictions you propose to apply to the TLD. Your description should should define the criteria to be employed, the manner in which you propose they be enforced, and the consequences of violation of the restrictions. Examples of matters that should be addressed are:
E17. Describe in detail the criteria for registration in the TLD. Provide a full explanation of the reasoning behind the specific policies chosen.
E18. Describe the application process for potential registrants in the TLD.
E19. Describe the enforcement procedures and mechanisms for ensuring registrants meet the registration requirements.
E20. Describe any appeal process from denial of registration.
E21. Describe any procedure that permits third parties to seek cancellation of a TLD registration for failure to comply with restrictions.
IV. CONTEXT OF THE TLD WITHIN THE DNS (Required for all TLDs)
E22. This section is intended to allow you to describe the benefits of the TLD and the reasons why it would benefit the global Internet community or some segment of that community. Issues you might consider addressing include:
E23. What will distinguish the TLD from existing or other proposed TLDs? How will this distinction be beneficial?
E24. What community and/or market will be served or targeted by this TLD? To what extent is that community or market already served by the DNS?
E25. Please describe in detail how your proposal would enable the DNS to meet presently unmet needs.
E26. How would the introduction of the TLD enhance the utility of the DNS for Internet users? For the community served by the TLD?
E27. How would the proposed TLD enhance competition in domain-name registration services, including competition with existing TLD registries?
V. VALUE OF PROPOSAL AS A PROOF OF CONCEPT (Required for all TLDs)
E28. Recent experience in the introduction of new TLDs is limited in some respects. The current program of establishing new TLDs is intended to allow evaluation of possible additions and enhancements to the DNS and possible methods of implementing them. Stated differently, the current program is intended to serve as a "proof of concept" for ways in which the DNS might evolve in the longer term. This section of the application is designed to gather information regarding what specific concept(s) could be evaluated if the proposed TLD is introduced, how you propose the evaluation should be done, and what information would be learned that might be instructive in the long-term management of the DNS. Well-considered and articulated responses to this section will be positively viewed in the selection process. Matters you should discuss in this section include:
E29. What concepts are likely to be proved/disproved by evaluation of the introduction of this TLD in the manner you propose?
E30. How do you propose that the results of the introduction should be evaluated? By what criteria should the success or lack of success of the TLD be evaluated?
E31. In what way would the results of the evaluation assist in the long-range management of the DNS?
E32. Are there any reasons other than evaluation of the introduction process that this particular TLD should be included in the initial introduction?
By signing this application through its representative, the Applicant attests that the information contained in this Description of TLD Policies, and all referenced supporting documents, are true and accurate to the best of Applicant's knowledge.
Signature
Henry
A. Lubsen, Jr.
Name (please print)
President
Title
iDomains,
Inc.
Name of Applicant(s)
September
30, 2000
Date
General TLD Policies
This
section provides a full and detailed description of all policies that will be
followed for the TLDs that iDomains is proposing. With the exception of the
proposals noted below, and except as mutually agreed upon with ICANN, iDomains
will implement all existing ICANN policies and operational functions of
Verisign Global Registry Services (VGRS) in the operation of the new TLD.
iDomains, Inc. proposes the following TLD strings in order of preference for a chartered top-level domain focusing on the enhancement of electronic commerce: ".BIZ", ".EBIZ", or ".ECOM".
Proposed Dual Co-Existent Naming System
iDomains proposes a dual co-existent naming system that will incorporate both second and third level domain name registrations. To facilitate this system, certain second level domains will be permanently retained by the registry to provide third-level domain name registrations.
Reserved Second Level Domain Names
All two-letter domains will be retained to replicate the existing country code top-level domain system. Further, a limited number of additional second level domains may be reserved to create a directory listing service within the top-level domain (e.g., sme.biz for small to medium enterprise business, .min.biz for minority-owned businesses, etc). These second level domains will be used to provide a hierarchical structure to the top-level domain that will be incorporated into a proposed directory service.
Multi-Level Registrations
The multi-level domain name registrations (second and third level) will be offered as a single package. A domain name registrant will be able to register a second level domain at the initial registration, and replicate that domain name as a third level domain in any relevant second level domain offered by iDomains. The domain name registrant will be given a choice of one free third level domain to register. The registrant will have the option to register additional third level domains pursuant to a fee schedule. Such registrant would be under no obligation to register such additional third-level domains, and the registrants string will be protected against registrations by other parties in the third levels offered by iDomains (in that no other registrant would be permitted to register third level domains using the same second level string).
The idea of this dual co-existent naming system was conceived to bridge the gap between the United States' general population, living primarily in a second level-world (domain-name.com), and the rest of the world that lives primarily in a third level domain world (e.g., domain-name.co.uk). iDomains recognizes that businesses throughout the world perceive value in publicizing their county of domicile in various manners, including the domain name under which they do business. For instance, businesses in South Korea or England may be more comfortable today doing business online using a third-level domain under .co.kr or .co.uk, respectively, rather than .com. Such registrants may find great value in being able to market their services under company-name.uk.biz or company-name.kr.biz. Further, such registrant could market to different geographical regions using different country-specific domains.
We strongly believe this dual co-existent naming system is both technically viable and culturally sensitive, and represents an excellent proof-of-concept for creative uses of the domain name system. Should ICANN's technical staff in its judgment believe that this dual co-existent should not be used during the proof of concept stage, we remain open to the idea of reserving the above referenced second level domain names for future use and roll-out the new top-level domain with second domain name registrations only. The exact nature and number of second level domains to be reserved will not be determined until iDomains is able to consult with its Business Advisory Committee (BAC) (described in Section E10 below) on the needs of the business community.
Will domain-name holders deal through registrars, directly with the
registry operator, or some
combination of the two?
We propose a process essential identical to the current registrant/registrar/registry relationship, domain name registrants will enter into domain name registration agreement (DNRA)with a qualified registrar who will then register the domain name on behalf of the registrant with iDomains. Prior to being eligible to provide domain name registration services to its customer, the registrar will have to enter into a registrar licensing agreement (RLA) that sets forth the contractual responsibilities that exist between the registrar and registry.
Each registrar, and any of its sales affiliates, will be required as part of their contractual obligations to disclose to domain name registrants the registrar of record along with certain minimum associated contact information to enhance customer confidence and service.
What are
the respective roles, functions, and responsibilities for the registry operator
and registrars?
iDomains will provide the same basic services as currently provided by VGRS except in the context of the following functions:
§ Unlike the current VGRS "thin" registry model that requires all Whois information to be maintained by the registrar, iDomains will employ a "thick" registry model.
§ Maintenance of a "thick" registry model will enable iDomains to provide significant enhancement to this proposed registry; that being a "UNIFIED WHOIS QUERY", a valuable functionality that currently is not available in the .COM, .ORG and .NET top-level domains, (the absence of which has resulted in fragmented Whois data availability).
§ iDomains also contemplates offering value added services to .BIZ domain name registrants. Such services would be provided by iDomains, or via third-party vendors. However, in order to adhere to the contractual relationships set forth above, either the registrar of record or the third party vendor will interact with the domain name registrant with a mutually agreed revenue sharing model. Such services could include Domain Name Monitoring and Service History Reports (as described in Section D13.2.1 of the Registry Operator’s Proposal).
§
In addition, iDomains will provide a "subscription
based" enhanced multi-field Whois search engine service. This service is primarily geared toward the
intellectual property community and associated businesses. We also intend to
provide this service to appropriate law enforcement agencies on a no charge
basis. This service will be available
to the registrars to resell to their customers.
§
Bulk access to the whois database would be available to
any ICANN accredited registrar for resale by such registrar to its
customers. Any resale by such registrar
would be subject to ICANN policies (e.g., the registrar could not charge more
than $10,000 per year for the data). Further,
the registrars would be required to obtain from the end user an agreement (in a
form approved by iDomains) to use the information only for lawful purposes and
in no event for purposes that would constitute abuse of the data, such as
facilitating high volume commercial e-mail.
As further protection against abusive uses of the bulk whois data, all e-mail addresses displayed in the bulk whois will be replaced in the form of CONTACT-HANDLE>@handles.registry.biz within the following guidelines:
E-mail received at <CONTACTHANDLE>@handles.registry.biz will be forwarded to the contact's real e-mail address. If the E-Mail address becomes invalid or bounces, the forwarding mechanism will be disabled and the contacts true e-mail address will be put into the bulk whois data.
This default mechanism
for all registrations is designed to enable spam prevention; however, upon
request of a registrant, such registrant may have their default changed to
disabled. The true and correct contact's e-mail address will be disclosed to
courts and police upon request.
Using the above policies will enable the registry to mitigate spam on the
behalf of registrants. Should a mass mailing be sent to registrants within the
.BIZ registry, the registry will be able to file appropriate legal action as
the e-mail addresses could have only been mined from the registry whois. We
believe that e-mail spam prevention and detection will become an industry
standard as we will be able to show just how much the whois database is used as
a source for spammer lists.
The .BIZ registry will
make available to the Internet Community additional statistics, sample spam,
and know spam origination sites. The .BIZ Registry will work with Industry
anti-spam and UCE prevention leaders such as RBL/Maps Project and other
anti-spam organizations to encourage the responsible use of whois data.
Fees collected by iDomains for provision of bulk whois service will be used to fund marketing projects designed to increase awareness of the .BIZ brand, and thus increase business for registrars, as well as the registry.
ICANN accredited registrars will have the same roles and functions as they currently do with regard to billing and customer support. The only differences will be those responsibilities associated with Whois and escrow requirements.
If registrars are to be employed, how and by whom
will they be selected or accredited?
iDomains will allow registrars that are accredited by ICANN to register in the .BIZ registry. However, iDomains will require such registrars to demonstrate their technical capability to properly interface with the registry prior to being able to register domain names in the ".BIZ" registry. iDomains will charge a small cost recovery based fee ( we are projecting in the area of $500.00) to defer its costs in connection with the technical interface compliance requirements.
If the
number of registrars will be restricted, what number of registrars will be
selected?
There will be no restriction on the number of registrars. All ICANN accredited registrars will be eligible to provide registration services in the .BIZ registry provided that they sign the RLA and meet the necessary minimum technical interface requirements.
Have the
qualifying registrars already been selected?
All ICANN accredited registrars will be eligible to provide registration services in the .BIZ registry provided that they sign the RLA and meet the necessary minimum technical interface requirements.
On what
basis will selections among those seeking to be registrars be made, and who
will make them?
All ICANN accredited registrars will be eligible to provide registration services in the .BIZ registry provided that they sign the RLA and meet the necessary minimum technical interface requirements.
If
registrars are to be used, what mechanisms will be used to ensure that TLD
policies are implemented?
iDomains will employ a registrar compliance liaison to proactively monitor registrar compliance with the RLA as well as aggressively investigating consumer or third party complaints.
What
measures will be taken to discourage registration of domain names that infringe
intellectual property rights?
iDomains will employ the following mix of measures to minimize abusive domain name registrations:
§ The use of a "Sunrise Program" to allow qualifying trademark owners to pre-register their respective trademarks as domain names;
§ Adoption of the Uniform Dispute Resolution Policy (“UDRP”) as promulgated by ICANN;
§ Requiring pre-payment prior to registering a domain name;
§ Stringent enforcement of domain name registrants providing and updating accurate Whois information;
§ Adopting a two-year minimum registration period;
§ Providing an enhanced subscription-based multi-field Whois queried database, as well as bulk whois access; and
§
Providing a Whois data watch service to notify domain
name registrants when any information contained in the Whois fields has
changed.
If you are proposing pre-screening for potentially
infringing registrations, how will the pre-screening be performed?
There will be no pre-screening of domain names with regard to potential intellectual property violations. During the Sunrise Period, however, registrants will be required (i) to represent that they have a valid registered trademark in the character string for which they apply, (ii) to provide the country from which such registration issued and (iii) to enter the registration number of such mark. Such information will assist the Internet community to ascertain the legitimacy of the registration.
Further, all registrants will be obligated to provide a national business tax identification number (or equivalent) prior to a domain name registration being added to the zone files. The exact nature of this requirement is set forth in more detail in Sections E.16 thru E.21.
What
registration practices will be employed to minimize abusive registrations?
iDomains believes the following practices, in addition to protecting intellectual property, will minimize abusive registrations: the institution of a Sunrise Program, the adoption of the UDRP, requiring pre-payment for registrations, requiring a minimum two-year initial registration, a commitment to stringent enforcement of accurate Whois data, and providing enhanced Whois search capabilities.
What
measures do you propose to comply with applicable trademark and
anti-cybersquatting legislation?
iDomains believes that by instituting a Sunrise Period, adopting the UDRP, requiring pre-payment for registrations, requiring a two-year minimum term for initial registrations, stringently enforcing the requirement that registrants maintain accurate whois data, and providing enhanced Whois search capabilities, in addition to minimizing abusive domain name registrations, will facilitate maximum compliance with applicable trademark and anti-cybersquatting legislation.
iDomains is committed to complying with all trademark and anti-cybersquatting legislation.
Are you
proposing any special protections (other than during the start-up period) for
famous trademarks?
Other than the Sunrise Program, detailed in Section E.15, iDomains does not propose any special protections for famous trademarks. As stated above, iDomains believes that by instituting a Sunrise Period, adopting the UDRP, requiring pre-payment for registrations, requiring a two-year minimum term for initial registrations, stringently enforcing the requirement that registrants maintain accurate whois data, and providing enhanced Whois search capabilities, will provide maximum protection for holders of registered trademarks worldwide.
How will
complete, up-to-date, reliable, and conveniently provided Whois data be
maintained, updated, and accessed concerning registrations in the TLD?
iDomains plans to provide a publicly accessible centralized Whois as a result of the "fat" nature of the registry. Because of the centralized location of the data, iDomains will undertake a regular scheduled statistical sampling of Whois data to guarantee its accuracy, as part of it charter enforcement guidelines. This sampling will employ the use of a variety of algorithms, i.e. missing data fields, address verification, check sum values, etc.
Any Whois inaccuracies or irregularities uncovered during this sampling will be forwarded to the appropriate registrar to correct. Failure to remedy inaccurate data in a timely fashion may result in the domain name being deleted.
As mentioned above, iDomains plans to offer a Whois data watch service to notify a domain name registrant of any changes in the Whois data fields. This feature is particularly useful in light of the recent rash of domain name hi-jacking incidents.
iDomains is also awaiting guidance from the ICANN Whois Taskforce with regard to technical considerations involving Whois data, and is closely following the international privacy directives involving Whois data. In light of these dynamic situations, iDomains stands ready to modify its Whois and privacy policies to meet the technical or legal directives established by the appropriate governing bodies.
To what
extent are you proposing to implement the Uniform Dispute Resolution Policy?
iDomains plans to adopt the
current Uniform Dispute Resolution Policy, as amended by ICANN from time to
time, in its entirety.
Please
describe any additional, alternative, or supplemental dispute resolution
procedures you are proposing.
According to the terms of the RLA, iDomains and its contracting registrars will be required to submit to binding arbitration for disputes arising out of the RLA.
Describe the proposed policies on
data privacy, escrow and Whois service.
iDomains is currently waiting guidance from the ICANN Whois and Escrow Taskforces with regard to these important issues. However, until such time that ICANN provides further instructions, iDomains will adhere to the following policies:
Data Privacy
iDomains is keenly aware of the international debate and dynamics involving individual privacy rights in Whois data. At this time, iDomains intends to comply with the terms of the ICANN-NSI Registry Agreement dated November 4, 1999. However, as a result of the chartered nature of the .BIZ top-level domain, registrants will be precluded from registering a domain name for non-commercial use in this domain. Therefore, concerns over individual privacy rights associated with Whois data should be minimized.
As part of any licenses to access the Whois data in bulk, there will be restrictions limiting the use of such data, (e.g., a prohibition against using the data to enable unsolicited commercial e-mail).
As further protection against abusive uses of the bulk whois data, all e-mail addresses displayed in the bulk whois will be replaced in the form of CONTACT-HANDLE>@handles.registry.biz within the following guidelines:
E-mail received at <CONTACTHANDLE>@handles.registry.biz will be forwarded to the contact's real e-mail address. If the E-Mail address becomes invalid or bounces, the forwarding mechanism will be disabled and the contacts true e-mail address will be put into the bulk whois data.
This default mechanism for all registrations is designed to
enable spam prevention; however, upon request of a registrant, such registrant
may have their default changed to disabled. The true and correct contact's
e-mail address will be disclosed to courts and police upon request.
Using the above policies will enable the registry to mitigate spam on the
behalf of registrants. Should a mass mailing be sent to registrants within the
.BIZ registry, the registry will be able to file appropriate legal action as
the e-mail addresses could have only been mined from the registry whois. We
believe that e-mail spam prevention and detection will become an industry
standard as we will be able to show just how much the whois database is used as
a source for spammer lists.
The .BIZ registry will make available to the Internet Community
additional statistics, sample spam, and known spam origination sites. The .BIZ
Registry will work with Industry anti-spam and UCE prevention leaders such as
RBL/Maps Project and other anti-spam organizations to encourage the responsible
use of whois data.
Escrow Service
iDomains will implement a data escrow policy as documented in the current ICANN-NSI Registry Agreement. Because of the "thick" nature of the .BIZ registry (all Whois information residing at the registry level), registrars will not be required to independently escrow Whois information for .BIZ domain name registrations. It is our understanding that ICANN is currently in the process of reviewing the “Escrow Process” with a goal of making it more uniform and efficient across-the-board. It is our intent to strictly adhere to any guidelines which may evolve thru the above mentioned review process.
Whois Service
iDomains will provide an interactive web page and a port 43 Whois service providing free public query-based access to up-to-date registry database. Additionally, iDomains contemplates providing an additional subscription service that will allow subscribers the ability to run complex queries across multiple fields. iDomains will closely monitor subscribers' usage to ensure that this feature is not being used inappropriately.
Finally, bulk whois access will be provided as described in Section E4 above.
Describe variations in or
additions to the policies for billing and collection.
iDomains will comply with current billing and collection practices, i.e. letter of credit, reasonable assurances of payment, refunds, etc. The only significant modification will be in connection with domains that are registered by the registrar but which are not paid for by the domain name registrant. In accordance with our proposed RLA, a registrar will have to delete a domain name after a “commercially reasonable” passage of time in which payment should have been received. In such a case, the registrar shall delete the domain name and it will immediately be released into the available domain name pool.
What registration services do you
propose to establish charges for and, for each such service, how much do you
propose to charge?
Registrars will not be required to pay a software licensing fee. However, iDomains will charge a small cost recover y based fee (Currently estimated to be approximately USD $500.00) to defer the cost of the registry in connection with the initial technical interface compliance requirements for each registrar. This process is similar to the technical certification that ICANN accredited registrars must pass prior to being able to go live with VGRS.
With regard to domain name pricing, iDomains will
require an initial minimum two year
registration period to minimize domain name speculation with a maximum term of
ten years. The registry fee for a single year domain name registration is
anticipated to be $5.45.
iDomains'
primary focus will initially be providing domain name registration services to
the registrars. We envision expanding
its scope of services to provide other services after the initial roll-out.
However, these services would not be designed to compete directly with our
established sales channels (the registrars). Some of these potential services
that iDomains may offer, include:
·
Enhanced
multi-field Whois queries - this would be a subscription service with an annual
single user fee of approximately two hundred dollars.
· Bulk Whois data access - provided as described in Section E4 above and Section D13.2.1 of the Registry Operator’s Proposal. We anticipate charging registrars $5,000 per end-user license for this service, which could be resold by the registrars to their customers. Any proceeds to iDomains from such service will be used to fund marketing projects designed to increase awareness of the .BIZ brand, and thus increase business for registrars, as well as the registry.
· A Whois data watch service to notify domain name registrants when any information contained in the whois fields has changed - iDomains may provide this service itself, or through third party vendors. No pricing has been determined at this time.
· As part of the dual naming system described in Section E3 above, iDomains envisions providing a directory service to the Internet community. It is possible a registrant will be afforded the opportunity to customize the information on its business in such directory on a fee basis, however no fee schedule has been developed at this time.
· IDomains plans to offer Service History Reports as described in Section D13.2.1 of the Registry Operator’s Proposal, however no fee schedule has been developed for such services at this time.
Please describe any policies
concerning topics not covered by the above questions
iDomains recognizes that ICANN has indicated that restricted top level domains normally should be sponsored. We believe that the full sponsorship model is not required for a top level domain developed for the commerce space. The policies inherent to such a model should not be markedly distinct from existing ICANN policies in our view. The .BIZ TLD is distinguished more from the services offered to registrants that the policies associated with the registry.
We also recognize, however, that there are advantages to drawing upon the knowledge and resources of a broad base of base of experts in global business issues. iDomains acknowledges that in order for this registry to fulfill its mission of promoting the development of e-commerce on a global scale, the registry must solicit input from experts from around the world. With this in mind, iDomains proposes to create a Business Advisory Committee (BAC) that with will provide recommendations on how to promote the responsible growth of e-commerce.
The BAC will have an advisory role to the iDomains Board of Directors similar to that of the relationship between ICANN and the Government Advisory Committee. It is estimated that the BAC will be composed of approximately 10 to 15 persons and that there will be proportional representation from each of the five ICANN geographic regions.
In preparing this registry proposal bid, iDomains has been in contact with numerous people involved with promoting e-commerce initiatives. Two people that have been extremely helpful in providing background information in connection with this bid have been Glynis D. Long from the US Small Business Administration, Office of Entrepreneurial Development and Eric Menge of the US Small Business Administration, Office of Advocacy.
iDomains has been in contact with both Mrs. Long and Mr. Menge about identifying people on a global scale that could potentially serve and make a contribution on the BAC. Once the BAC is in place, iDomains will be able to effect serious initiatives toward promoting e-commerce more effectively on a global scale.
iDomains plans on contributing approximately five percent (5%) of its annual pre-tax profits to a fund to be administered by the BAC and allocated for the development and enhancement of global commerce initiatives.
Registration
Policies During The
Start-Up Period
This section describes all policies (including implementation details) that iDomains proposes during the start-up phase of registration in the TLDs.
How do you propose to address the
potential rush for registration at the initial opening of the TLD?
iDomains intends to use a combination of mechanisms to handle the potential rush for registration that might otherwise threaten the stability of the registry. The two primary tools that will be used are the rotational "round robin" system (explained in detail below) and the Sunrise Program.
Rotational "Round Robin" System:
Although iDomains' normal registration system will register domain names on a first come first serve basis in real time, the realities of rolling out a new top-level domain dictate that a modified system be used to handle the contemplated land rush phenomenon.
The basis of the rotational "round robin" system involves a method by which registrars accept pre-registration that are then submitted to the registry in batch files and then processed by the registry using a queue system. The details of this system are outline in more detail below.
Qualified registrars would begin by accepting pre-registrations from domain name registrants. The registrar would then compile these domain names and the associated Whois data into batch files for submission to the registry. When the registry was ready to accept domain name registrations, the registry would query each registrar to get its initial batch file. These batch files would then be securely transferred to the registry for processing off-line, i.e. no open secure connection between the registry and the registrar.
After obtaining these batch files, the registry would then undertake the task of randomizing the batch files, and then processing these domain name requests names one application per registrar in a random order. Independent of the random order of the registrar ranking in each round, no registrar will have the opportunity to request and register more than one domain name per round. iDomains feels that this methodology will dissuade registrars from “selling” places in their respective queues, a practice is unacceptable in the opinion of iDomain’s management.
If a registrar's request for a domain name registration is denied, the registry will request the next available domain name registration in the batch file until a domain name is successfully registered or the registrar has no more requests in the batch. Once a registrars batch file is depleted, the registry will contact the registrars to look for another available batch file.
We remain open to other suggestions from ICANN as well as input from the Internet community at large for methods to enhance the equitable and reliable features of this rotational round-robin feature.
Sunrise Program:
A detailed description of the Sunrise Program that iDomains envisions providing is set forth in Section E.15.
How
many requested registrations do you project will be received by the registry
operator within the first day, week, month, and quarter?
iDomains estimates the following domain name registration volumes upon the initial opening of the registry to the public (i.e., after the conclusion of the Sunrise Period):
i) 75,000 on the first day;
ii) 200,000 within the first week;
iii) 300,000 within the first month; and
iv) 712,500 within the first quarter.
What
period do you believe should be considered the TLD's "start-up period,"
during which special procedures should apply?
iDomains estimates being able to move to a traditional first come first serve registry model within twenty (20) to thirty (30) days of going live. However, this date may have to be adjusted accordingly to account for demand and system resources.
Do you propose to place limits on
the number of registrations per registrant? Per registrar? If so, how will
these limits be implemented?
iDomains does not intend to limit the number of registrations per
registrant and per registrar at any time, including during the start-up
period.
Will pricing mechanisms be used to
dampen a rush for registration at the initial opening of the TLD? If so, please
describe these mechanisms in detail.
iDomains contemplates using no special pricing mechanism during the initial roll-out of the registry. iDomains feels strongly that the existing rotational "round robin" system coupled with the Sunrise Program will provide a fair and equitable solution that will not compromise the stability of the registry's operations.
Will you offer any "sunrise
period" in which certain potential registrants are offered the opportunity
to register before registration is open to the general public?
During the start-up phase, iDomains will provide a Sunrise Program that
will afford protection to qualifying trademark owners prior to the top-level
domain going live. The program is broken down into the following three periods.
Announcement Period: At least ninety (90) days
prior to .BIZ being added to the root server system, the iDomains, in
coordination with the intellectual property community will make a general
public announcement with the estimated go-live date. This Announcement Period
will last for a minimum of 30 days, although it can be extended depending upon
the commencement of the general public announcement. However, under no
circumstance will the Registration Period begin until the trademark community has
had at least 30 days public notice.
Registration Period: Following the Announcement Period and at least sixty
(60) days prior to the proposed TLD being added to the root, the registry will
begin the Registration Period where it will begin processing domain name
registrations in a controlled, equitable manner among eligible trademark owners
through previously accredited
registrars. This registration period is scheduled to last for a minimum of
30-60 days. Following the close of the Registration Period we will implement a
“Cooling Off” period in which no additional domain name registrations will be
accepted by registrars.
Cooling Off Period: After the Registration Period, there will be at least a minimum
thirty (30) day cooling off period in which the registry will complete any
outstanding Sunrise program registrations. This period will also provide
trademark owners with the opportunity to investigate any fraud by domain name
registrants and initiate a challenge (see below). This Cooling Off
Period will also serve to provide the Registry with the opportunity to make any
necessary modifications to the registry software prior to open the
registrations to the general public.
Eligibility to Participate in Sunrise Period:
Any legitimate owner of any valid registered trademark or service mark
registration having national effect would be eligible to seek to registration
of that mark, and that mark alone, as a domain name during the Sunrise
Program, provided that the registration for that mark issued on an application
filed prior to October 2, 2000. The domain name registration would be
confined to a single registration corresponding to a trademark. The Sunrise
Program domain name registrations have to be identical to the material textual
element of the registered trademark, excluding disclaimed words associated with
design marks. Domain name registrations during this Sunrise Period will be for
a minimum of Three (3) years.
Required Additional Whois Data
In order to register a domain name during this Sunrise Period, a
registrant must electronically acknowledge that it is the owner of a valid,
national trademark registration that issued on an application filed prior to
October 2, 2000. In addition, the
registrant must supply the following: the name of the trademark; date of
registration; country of registration, and registration number. Neither the
registrars nor iDomains will verify any information initially provided by the
trademark owner registrant prior to registering the domain names. These
additional data elements will be maintained in a modified Whois database to
provide the public at large with the ability to investigate any domain names
registered during this Sunrise Program. This is to afford potentially aggrieved
trademark owners with the ability to independently verify the veracity of the
information provided by another.
Challenges During Sunrise Program by Competing Trademark Interest
If a third party independently investigates the trademark information
provided by the domain name registrant and believes it to be erroneous, such
party may file a challenge with iDomains with respect to that domain name along
with the submission of a challenge fee (currently estimated to be $100
US). iDomains will then request from
the registrant proof of its valid trademark registration having national
effect. If the domain name registrant
is unable to provide evidence of a valid trademark registered prior to October
2, 2000, iDomains will cancel the domain name registration. In such case, the registrant will not be
entitled to any refund of registration fees paid. If the party that filed the first challenge with respect to a
given domain name registration is the owner of a valid trademark registration
that would qualify such challenger to register the disputed domain name during
the Sunrise Period, iDomains will give such party the first right to register
the domain name, using the services of the registrar of such party’s
choice. Further, in such event, the
challenger will receive a refund of the challenge fee. However, if the information provided by the
domain name registrant is accurate, the challenging party will forfeit the
challenging fee.
Challenges Following the Sunrise Program by Competing Trademark
Interest and Third Parties
Following the conclusion of the Sunrise Program, after the new top
level domain is added to the root server system, any party with a competing
trademark interest will be permitted to initiate a challenge as set forth above
for up to one year. After such one year
period had expired, a party challenging a Sunrise Period registration will need
to proceed under the UDRP or applicable law.
This section describes in detail the restrictions that iDomains
proposes to apply to the .BIZ TLD, including the criteria that will be
employed, the manner in which it will be enforced, and the consequences of
violation of the restrictions.
Describe in detail the criteria
for registration in the TLD. Provide a full explanation of the reasoning behind
the specific policies chosen.
iDomains
recognizes that the development of chartered top-level domain devoted toward
e-commerce would be closely scrutinized to guarantee that it was not simply an
attempt to mimic the .COM phenomenon. With this in mind, iDomains set out to
develop strict compliance mechanisms both on the front end and back end of the
registration process.
It is through
the use of these enforcement mechanisms that iDomains would be able to
guarantee the level of consumer confidence that Internet users are seeking.
Although the .COM TLD was originally designed to handle commercial activity,
due to the lack of effective charter enforcement, .COM has become everything to
everybody. Although this phenomenon was instrumental in the rapid pace with
which the Internet grew, the Internet is now evolving into a commercial
marketplace where consumers require increased confidence in the businesses with
which they transact business. It was
this unmet need that was the genesis behind the iDomains proposal.
Because of the
focus on promoting electronic commerce, iDomains originally contemplated
various front-end screening mechanisms, such as requiring an online credit card
processing capability. However,
consultation with Mrs. Long and Mr. Menge at the US Small Business
Administration confirmed our belief that we needed to keep the charter broad
enough so that our restrictions would not operate as an arbitrary mechanism by
which a significant portion of global small businesses would be disenfranchised,
including many businesses just beginning to venture out on the Internet
(particularly in third-world countries and emerging global electronic commerce
economies such as China). Therefore, we
have focused on maintaining a balance between restricting the TLD to truly
commercial uses and permitting small businesses worldwide to enjoy the benefits
of this new name space.
Listed below are
some of the statistics that iDomains reviewed in connection with analyzing the
impact of e-commerce on small businesses. The significant amount of resources
devoted to investigating e-commerce and small business on a global basis
demonstrates that this is this segment of the global business community that
need the biggest boost in being able to capitalize on the new economy.
http://www.sba.gov/advo/stats/e_comm2.pdf
http://www.sba.gov/advo/stats/e_comm.pdf
http://www.sba.gov/advo/stats/thirdmill.pdf
http://www.sba.gov/advo/stats/answer.pdf
http://www.sba.gov/advo/stats/facts99.pdf
http://www.sba.gov/advo/stats/ch_em97.pdf
http://www.sba.gov/advo/stats/wib.pdf
http://www.sba.gov/advo/stats/min.pdf
http://www.sba.gov/advo/stats/ind88_95.pdf
http://www.sba.gov/advo/stats/exp_rpt.pdf
Following the
discussions with Mrs. Long and Mr. Menege, iDomains decided to adopt a more
flexible screening mechanism on the front end coupled with a creative backend
sampling of Whois data to identify erroneous and fraudulent data.
Front-End
Screen Mechanism
The front-end
mechanism will require the domain name registrant to provide a governmental
taxing ID (i.e. EIN, VAT number, etc.) prior to the domain name being added to
the active zone files. However, in light of the fact that many small businesses
get started without first obtaining the appropriate taxing ID, iDomains
recognized the need to be flexible in this solution. In response, iDomains decided after careful consideration
to allow domain name registrants to register a domain name without the
appropriate taxing ID information. Prior to the domain name being activated to
the zone files, however, the domain name registrant will be required to provide
the required taxing ID information.
Back-End
Sampling Mechanism
Additionally,
iDomains intends to use a creative array of algorithms to scan the centralized
Whois database for erroneous or fraudulent data. In addition, iDomains will
under take the sampling of select data to verify its accuracy. This in
conjunction with a pro-active enforcement liaison will enhance greatly the
level of confidence that consumers seek.
Describe
the application process for potential registrants in the TLD.
As mentioned above, domain name registrants seeking to register a domain name would have to interact with an authorized registrar. In addition to providing the standard Whois data, the potential domain name holder would have to provide a taxing ID from a competent national authority for direct inclusion into the root zone files. Domain name registrants, particularly SMEs may not have ready access to these taxing IDs, can elect to register a domain name without a taxing ID number. However, before this domain name can be added to the zone files for update to the root server system, the domain name registrant must provide the registry with requisite information.
iDomains is aware that there are certain countries or territories where companies will not have taxing ID numbers. In those situations, iDomains will work to tag these entries in the database to allow for the activation of the domain names into the zone files. In these situations, iDomains will closely follow the registrant practices in those countries to prevent it from becoming a haven for abusive domain name registrants.
After providing the necessary taxing information, the domain name will be added to the zone files. Although iDomains will be employing a "thick" registry model, domain name registrants will have to interact with authorized registrars to make any changes associated with the administration of that domain name.
As part of the ongoing sampling process, iDomains will be looking for questionable data. In circumstances where there exists potential faulty data, the registry will require the registrar of record to investigate the accuracy of the data. iDomains will also maintain as part of the registry website an information page to report potential charter violations.
Describe the enforcement
procedures and mechanisms for ensuring registrants meet the registration
requirements.
iDomains will use a variety of enforcement mechanisms both on the front end and back end registration process. The front-end mechanism will require the domain name registrant to provide a taxing ID from a competent authority. On the back-end, the registry will employ a host of algorithms to identify questionable data, i.e. checksum values, address verification, etc.
With regard to charter violations, i.e. a domain name NOT being used in accordance the charter, the preferred method of recourse is to file a Dispute Proceeding with an accredited provider. iDomains has begun preliminary discussion with dispute providers to identify the cost associated with these decisions. However, in charter violations where there is no genuine issue of material fact, iDomains reserves the right to take immediate action if it is so justified. This reservation of rights will be incorporated into the DNRA along with other provisions that limit the damages associated with such action.
To minimize the cost associated with these administrative proceeding there will be no requirement for a written opinion.
Describe any appeal process from
denial of registration
In any situation where a registrant is denied a domain name registration in the .BIZ TLD, the registrant will be eligible to file an administrative proceeding with a qualified Dispute Provider (most probably accredited Dispute Providers already authorized by ICANN) to challenge the rejection. In any such challenge, the domain name registrant will bear all fees associated with this challenge, estimated to be approximately $1,000.
To minimize the cost associated with these administrative proceeding there will be no requirement for a written opinion.
Describe any procedure that
permits third parties to seek cancellation of a TLD registration for failure to
comply with restrictions.
In the case of charter violations where there is no genuine issue
of material fact, iDomains reserves the right to take immediate action (placing
a domain name on hold or canceling it) if it is so justified. This reservation
of rights will be incorporated into the Domain Name Registration Agreement
(DNRA) along with other provisions that limit the damages associated with such
action.
In any situation where a third party seeks to cancel a domain name for a purely
charter violation (no underlying intellectual property issues), and a
determination is made that there is a genuine issue of material fact between
the domain name registrant and the third party, then the third party will have
the opportunity to seek an administrative proceed to make a final
determination. The domain name registrant will be bound to submit to the
authority of this Dispute Provider under the terms of the DNRA. However, the
third party will have to bear all costs and fees associated with this
administrative proceeding, estimated to be approximately $1,000.
This section describes the benefits of the .BIZ TLD and the reasons why it would benefit the global Internet community.
What will distinguish the TLD from
existing or other proposed TLDs? How will this distinction be beneficial?
However as the Internet evolves and
revolutionizes the manner in which we conduct commercial transaction, the need
for consumers to be confident in the medium with which they are dealing is
crucial. Several of the US Small Business Administrative references listed
above cite security concerns as one of the leading impediments toward
preventing the further growth of Internet commerce.
Moreover, as the Internet evolves into a global
marketplace, there is the need for clearer sign posts for what is and is not
intended for commercial activity, and the potential further qualification of
what type of commercial activity.
The charter nature of our proposed TLD is
designed to distinguish itself from other potential commercial business
registry bidders that seek to operate the registry as a “generic” top-level
domain. The chartered nature of our
proposed registry coupled with the
proposed dual co-existent naming system as outline in Section E.3 is designed
to provide further hierarchical structure to the .BIZ domain space for the
benefit of consumers and merchant attempting to engage in electronic commerce.
What community and/or market will
be served or targeted by this TLD? To what extent is that community or market
already served by the DNS?
Businesses
The very nature of the .BIZ TLD is to promote and stimulate e-commerce initiatives. iDomains is seeking to do this by creating a "branded" commercial space where consumers can shop with increased confidence.
Although the .COM revolution was well chronicled in the media, most Internet users are not much advanced past the neophyte stage with regard to online transactions
iDomains commitment to the development of global commerce is evidenced by the proposal to contribute five percent (5%) of the Company’s profit before taxes each year for the furtherance of global business initiatives worldwide as recommended by the Business Advisory Committee (BAC). It is envisioned that some of the initiatives that the BAC might consider include: increased use of digital signatures, minimizing credit card fraud, consumer privacy, Code of Conduct for participant members, etc.
Consumers
By creating a global commercial interchange, iDomains will help foster an environment that allows consumers to buy online with the confidence they enjoy while using their credit cards in their day to day activities. Moreover, coupled with the recent passage of the digital signature in the United States, consumers are able to build their confidence online. Further, as referenced above, it is envisioned that the BAC might propose Code of Conduct requirements with regard to privacy issues.
Please describe in detail how your
proposal would enable the DNS to meet presently unmet needs.
As repeated throughout this Policy Section, .COM lost its is "source identifier function" as a result of NSI's historical failure to enforce the nature of the charter. Since the dilution of .COM, the Internet has become a dot com waste land of information with little or no intuitive direction.
iDomains strongly believes that the future growth of the DNS will center around chartered and sponsored TLDs as opposed to an explosion of generic TLDs, and it is these chartered domains that will begin to set the meets and bounds of certain voluntary zoning.
The proposed dual naming system provides a hierarchical structure to the name space that is ideally suited for directory service. In addition, this dual co-existent naming system was conceived to bridge the gap between the United States' general population that lives primarily in a second level-world (domain-name.com), while the rest of the world lives in a third level domain world, (e.g., domain-name.co.uk).
The details of this dual naming system is set forth in Section E.3.
How would the introduction of the
TLD enhance the utility of the DNS for Internet users? For the community served
by the TLD?
As referenced above the creation of a "branded" commercial venue is greatly needed to help Internet users understand the differences between the various competing top-level domains. Most Americans live is a .COM second level domain world, few understand the nuisances of country code extensions or of the third level domain name registration
Under the dual co-existent naming system being proposed, iDomains believes that a directory listing service can be created of incredible value, independent of the current dotcom directory.
The other area where industry will be quick to incorporate these new DNS TLDs is in connection with search engine and browsers.
How would the proposed TLD enhance
competition in domain-name registration services, including competition with
existing TLD registries?
.COM's biggest asset is also its biggest liability. Because of the over crowding of the .COM universe, businesses are having an increasingly difficult time finding acceptable domains names that are available for use. The addition of .BIZ to the name space will immediately provide a host of new domain name options for registrants.
In addition, iDomains proposes to operate a “fat” registry model for .BIZ, a model that will enhance security, reliability and efficiency of the name space, providing an attractive domain name option for potential business registrants. Further, iDomains plans to offer an array of value added service, some at no additional charge and some on a fee basis, that will provide better functionality for registrants.
An additional element of iDomains’ proposal that is likely to enhance competition is the incorporation of a third level domain system into the registry functionality. Registrants will be afforded the flexibility of marketing their products and services under a second level domain (e.g., company-name.biz) or under one or more geographically specific domains (e.g., company-name.de.biz). We believe that this aspect of the .BIZ registry service will be very attractive to registrants on a global scale.
Finally, among the intermediate term goals for iDomains is to work with our BAC to sponsor global workshops designed to develop methods and procedures to meet various needs of the online business community, such as credit card fraud reduction and consumer privacy enhancement. Our goal is to develop a Code of Conduct for registrants that would ultimately operate as a “seal of approval” type certification process, building consumer confidence and the .BIZ brand concurrently.
This section defines specific concepts that could be used in evaluating the Registry Bid how to evaluate the process.
What concepts are likely to be proved/disproved by
evaluation of the introduction of this TLD in the manner you propose?
·
A
charter can be successfully launched in a niche commercial market and compete
head on with the .COM directory;
·
A
"thick" registry provides a more reliable registry environment with
regard to whois and escrow services;
· That some businesses will shed their cumbersome .COM in favor of a more appealing .BIZ domain name;
·
The
Sunrise Program was an effective tool in minimizing abusive domain name
registrations;
How do you propose that the results
of the introduction should be evaluated? By what criteria should the success or
lack of success of the TLD be evaluated?
iDomains believes that the following factors are important elements that need to be considered in the evaluating the success of the TLD. The first benchmark to be evaluated is the total number of domain name registered over a three year period. The reason for the three-year period is that it allows iDomains to evaluate what a domain name holder will do when their original two year domain name registration comes up for renewal. If there is a significant attrition rate among domain name renewal registrants, then this could be a negative factor in the long-term viability of the registry.
The beginning of the fourth year is another critical benchmark as it is the renewal period for trademark owners that participated in the Sunrise Program at the basic three-year registration. A significant decrease in these numbers may not be evidence of decreased popularity of the .BIZ TLD but increased confidence in the trademark community about not being required to register every variation of its trademark to guard against cybersquatters. Another important benchmark to scrutinize is domain name registration volumes on a quarterly basis. In most businesses there is a "honeymoon" period where a business owner can do no wrong. However, the long-term success of a business can only be evaluated by comparing its long comparative sales figures.
iDomains will also track the domain name
registration volume from the other new and existing top-level domains with
particular attention focusing on top-level domains of a commercial
nature. There will be a compelling need to analyze the registration trends of
existing domain name holders in these new top-level domains. If the same
businesses that have my-second-level-domain.com register this same second level
domain in each of the other new registries, there is little argument that the
domain name space was expanded. In fact one could argue that it was merely
duplicated. The number of UDRP filing
will be important to gauge the effect of the Sunrise Program and UDRP. The number and geographic diversity of the
registrars that register opt to register domain names in the .BIZ TLD. This
will help gauge the regional acceptance of this new top-level domain by the
Internet community at large.
In what way would the results of
the evaluation assist in the long-range management of the DNS?
By gauging the number of registration in
a charted and generic TLD it will
provide ICANN with valuable information on market demand for potential
special interest commercial segments. In making this analysis it is
important to compare "apples to apples." Because .COM is considered
the default commercial top-level domain, it is important that ICANN make this
comparison with a charted commercial top-level domain name as opposed to a
non-profit or special interest top-level domain.
iDomains believes that the Sunrise Program in conjunction with the UDRP will
demonstrate to the Internet community the necessary balance required between
the intellectual property community and the Internet stakeholders. Minimizing
potential legal liabilities is crucial to the long- term viability of a
registry. The success of these programs will be directly measure in the number
of UDRP filings in connection with the .BIZ top-level.
IDomains believes that the use of the dual co-existing naming system, will
provide a logical directory system for global e-commerce. The proposed
directory system will allow Internet users to quickly access the location and
content matter of a business simply by referencing a domain name.
Another important evaluation criteria
will be the number of domain name registrants that have the same name in .BIZ
and other top-level domains. This evaluation is likely to reveal either one of
two trends.
The first being that domain name registrant are just duplicating their second
level domain registrations in other new top-level domains. In such a case, it
would be hard pressed for someone to argue that the name space was expanded
since all the same second level text strings are owned by the same entity in
different top-level domains.
The second possible trend is that there is that there is a diversity of second
level domain name registrant for the same string in different top-level
domains. In this scenario, there would be a strong prima facie case that the
name space had been expanded.
In light of the recent letter from the NTIA of the United States Department
of Commerce, there appears to be a strong need for unified and enhanced
Whois search features.
Are there any reasons other than
evaluation of the introduction process that this particular TLD should be
included in the initial introduction
iDomains believes that the current domination of the
TLD space by large businesses presents an
image for the future that is quite troubling to many small and medium size
business organizations throughout the world.
The opportunity for future global growth in spaces like the commercial space cannot be dominated by just the “Big Guys”. Our TLD model provides a methodology for policy development and guidance which embraces, on a global basis, businesses of all sizes and structures
We believe that we bring
technical expertise and resources, a strong financial base and acumen, as well
as the appropriate DNS experience to most effectively deal with this proposed
proof-of- concept solution.